Generating emergency vehicle warnings

ABSTRACT

The present disclosure generally relates to generating emergency vehicle warnings, alternate vehicle routing recommendations and/or insurance-related data based upon emergency vehicle warning data. More particularly, the present disclosure relates to generating data representative of emergency vehicle warnings and/or alternate routing based upon real-time information related to an emergency vehicle. The information related to the emergency vehicle may include emergency vehicle origination location data, emergency vehicle current location data, emergency vehicle route data, and/or emergency vehicle destination location data. An emergency vehicle warning and/or alternate vehicle routing for non-emergency response vehicles may be generated based further on information related to a non-emergency vehicle. In one aspect, an emergency vehicle may wirelessly communicate with the non-emergency vehicle and/or an insurance provider remote server. The insurance provider may adjust auto insurance for insureds having vehicles with the vehicle safety functionality discussed herein to reflect lower risk and provide insurance savings to customers.

CROSS REFERENCE TO RELATED APPLICATION

This applications is a continuation of, and claims the benefit of, U.S.patent application Ser. No. 14/694,498, filed Apr. 23, 2015 and entitled“Generating Emergency Vehicle Warnings,” which claims priority, under 35U.S.C. § 119(b), to U.S. Provisional Patent Application Ser. No.62/107,745, filed on Jan. 26, 2015, and entitled Methods and Systems forGenerating Emergency Vehicle Warnings, the disclosures of which areincorporated herein by reference in their entireties. This applicationis also related to U.S. patent application Ser. No. 14/694,493 (now U.S.Pat. No. 10,008,111), filed on Apr. 23, 2015 and entitled GeneratingEmergency Vehicle Warnings; U.S. patent application Ser. No. 15/918,123filed Mar. 12, 2018 (now U.S. Pat. No. 10,176,716); and U.S. patentapplication Ser. No. 16/197,564 filed Nov. 21, 2018.

TECHNICAL FIELD

The present disclosure generally relates to methods and systems togenerate emergency vehicle warnings. More particularly, the presentdisclosure relates to generating data representative of emergencyvehicle warnings based upon real-time information related to anemergency vehicle, and/or insurance-related data based upon emergencyvehicle warning data.

BACKGROUND

Emergency response vehicles are often slowed down on their way to firesand accidents by other vehicles that do not move out of the way. Newercars have better sound-proofing and drivers maybe listening to loudmusic which prevents them from hearing approaching sirens. Additionally,not all people know where to move to get out of the way of emergencyvehicles. This condition (blocked roads) often slows first responderswhen time is of the essence. These circumstances may lead to accidentsand collisions between emergency responders and other vehicles.

Additionally, conventionally lights and sirens have long been used toalert drivers of approaching EMS vehicles. Lately, with some vehicles,the sirens have been moved from the top of emergency trucks to bumperlevel in order to direct the associated sound and illumination towardother drivers. However, there are still deficiencies associated withthese systems, such as drawbacks related to accidents and time.

SUMMARY

Systems and methods are provided for generating data representative ofemergency vehicle warnings, and/or generating data representative ofinsurance policies based upon data representative of emergency vehiclewarnings. The systems and methods may reduce EMS/auto collisionaccidents, speed response time (e.g., fire trucks, ambulances, police,etc.) which might reduce fire losses, and/or faster response to autoaccidents may reduce injuries/save lives.

In one aspect, a computer implemented method for generating datarepresentative of an emergency vehicle warning and/or alternate vehicleroute may be provided. The method may include (1) receiving, via or atone or more processors mounted on a non-emergency vehicle, emergencyvehicle data via wireless communication and/or data transmission,wherein the emergency vehicle data is representative of: emergencyvehicle (i) origination location, (ii) current location, (iii) currentroute, (iv) current destination, (v) current speed, and/or (vi) type ofemergency, such as vehicle accident, house fire, or other emergency: (2)generating or collecting, via or at the one or more processors mountedon the non-emergency vehicle, non-emergency vehicle data, wherein thenon-emergency vehicle data is representative of: non-emergency vehicle(a) origination location, (b) current location, (c) route data, (d)destination, and/or (e) speed; (3) determining or generating, via or atthe one or more processors mounted on the non-emergency vehicle,emergency vehicle warning data and/or an alternate vehicle route databased upon computer analysis or comparison of the emergency andnon-emergency vehicle data, the alternate vehicle route directing thenon-emergency vehicle to avoid the route of the emergency vehicle orotherwise alleviates an amount that the non-emergency vehicle interfereswith the route of the emergency vehicle; and/or (4) causing, via or atthe one or more processors mounted on the non-emergency vehicle, theemergency vehicle warning data and alternate vehicle route data, to bevisibly or audibly presented, or otherwise provided, to a driver of thenon-emergency vehicle (or to the non-emergency vehicle itself) tofacilitate alleviating potential vehicle accidents between emergencyresponse and non-emergency response vehicles, and/or shorteningemergency response times for emergency vehicles.

The method may include generating, via the one or more processorsmounted on the non-emergency vehicle, insurance policy data for thedriver of the non-emergency vehicle based upon the driver followingrecommendations associated with emergency vehicle warnings or alternatevehicle routing that avoids emergency vehicles en route; and/ortransmitting, via the one or more processors mounted on thenon-emergency vehicle, to an insurance provider remote server tofacilitate the insurance provider providing auto insurance cost savingsto the driver (or other insured) based upon the insurance policy dataand/or functionality associated with emergency vehicle avoidance. Theinsurance policy data may be representative of an insurance riskassociated with a non-emergency vehicle, and/or the insurance risk maybe lower for a non-emergency vehicle that is equipped with an emergencyvehicle warning data receiving device. Additionally or alternatively,the insurance policy data may be representative of an insurance riskassociated with an emergency vehicle, and/or the insurance risk may belower for an emergency vehicle that is equipped with an emergencyvehicle warning data generation, transmitting, and/or receiving device.

The method may include transmitting, via the one or more processorsmounted on the non-emergency vehicle, emergency vehicle warning data andalternate vehicle route data to other vehicles or processors. In oneembodiment, the non-emergency vehicle may be an autonomous,semi-autonomous, or smart vehicle. The autonomous, semi-autonomous, orsmart vehicle may automatically direct itself to take an alternatevehicle route and/or take self-driving actions that allow theautonomous, semi-autonomous, or smart vehicle avoid the emergencyvehicle or the route of the emergency vehicle. Alternatively, theemergency vehicle may be an autonomous, semi-autonomous, or smartvehicle, and the autonomous, semi-autonomous, or smart vehicleautomatically may direct itself to take an alternate vehicle route andtake self-driving actions that allow the autonomous or smart vehicleavoid the non-emergency vehicle or the route of the non-emergencyvehicle.

The method may further include adjusting an insurance policy, premium,rate, or discount for the non-emergency vehicle based upon thenon-emergency vehicle having the vehicle warning and/or alternatevehicle route generation functionality discussed herein. The method mayinclude additional, less, or alternate functionality, including thatdiscussed elsewhere herein, and/or the method may be implemented via acomputer system, communication network, one or more processors, and/orcomputer-executable instructions stored on non-transitory storage mediaor computer-readable medium.

Advantages will become more apparent to those skilled in the art fromthe following description of the preferred embodiments which have beenshown and described by way of illustration. As will be realized, thepresent embodiments may be capable of other and different embodiments,and their details are capable of modification in various respects.Accordingly, the drawings and description are to be regarded asillustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The Figures described below depict various aspects of the systems andmethods disclosed herein. It should be understood that each figuredepicts an embodiment of a particular aspect of the disclosed systemsand methods, and that each of the figures is intended to accord with apossible embodiment thereof. Further, wherever possible, the followingdescription refers to the reference numerals included in the followingfigures, in which features depicted in multiple figures are designatedwith consistent reference numerals.

There are shown in the drawings arrangements which are presentlydiscussed, it being understood, however, that the present embodimentsare not limited to the precise arrangements and instrumentalities shown,wherein:

FIG. 1 depicts an exemplary system for generating emergency vehiclewarning data and/or insurance-related data based upon the emergencyvehicle warning data;

FIG. 2 depicts a high-level block diagram for an exemplary computersystem for generating emergency vehicle warning data and/orinsurance-related data based upon the emergency vehicle warning data;

FIG. 3 depicts a block diagram for an exemplary emergency vehicle devicefor generating emergency vehicle data and/or emergency vehicle warningdata;

FIG. 4 depicts a block diagram for an exemplary non-emergency vehicledevice for generating non-emergency vehicle data and/or emergencyvehicle warning data;

FIG. 5 depicts a block diagram for an exemplary remote emergencymanagement services computing device for generating emergency vehiclewarning data and/or insurance policy related data based upon theemergency vehicle warning data;

FIG. 6 depicts a flow diagram for an exemplary method for generatingemergency vehicle data and/or emergency vehicle warning data;

FIG. 7 depicts a flow diagram for an exemplary method for generatingnon-emergency vehicle data and/or emergency vehicle warning data, and

FIG. 8 depicts a flow diagram for an exemplary method for generatingemergency vehicle warning data and/or insurance policy related databased upon the emergency vehicle warning data.

The Figures depict preferred embodiments for purposes of illustrationonly. One skilled in the art will readily recognize from the followingdiscussion that alternative embodiments of the systems and methodsillustrated herein may be employed without departing from the principlesof the invention described herein.

DETAILED DESCRIPTION

An emergency vehicle location alert may be provide using a systemsimilar to the nationwide text emergency alert system, called WirelessEmergency Alerts (WEA) implemented by the National Weather Service, toprovide emergency alerts to, for example, cellular telephones. Vehiclesin a path of police, fire trucks, and ambulances, etc. may, thereby, bewarned of impending emergencies. WEA-capable telephones may be providedto deliver just-in-time driver alerts that warn of approaching EMSvehicles. The alerts may be tailored with messages, such as “stop,”“move right,” “move left,” “move onto the shoulder,” “merge to rightlane,” and/or the like, or just duplicate a siren tone, to clear theroad ahead. Additionally or alternatively, non-emergency vehicles may beautomatically or manually re-routed to clear the path of emergencyresponse vehicles. Algorithms may be provided to determine a relativeposition of Emergency Management Services (EMS) vehicles and localtraffic so as to not unduly warn and/or re-direct cars not in the pathof travel of the EMS vehicles.

Accordingly, the systems and methods of the present disclosure generallyrelate to generating emergency vehicle warnings (and/or alternatevehicle routing). More particularly, the methods and systems relate togenerating data representative of emergency vehicle warnings (and/oralternate vehicle routing) based upon real-time information related toan emergency vehicle. The information related to the emergency vehiclemay include, for example, emergency vehicle origination location data,emergency vehicle current location data, emergency vehicle route data,and/or emergency vehicle destination location data. An emergency vehiclewarning may be generated based further upon information related to anon-emergency vehicle. The information related to the non-emergencyvehicle may include, for example, non-emergency vehicle originationlocation data, non-emergency vehicle current location data,non-emergency vehicle route data, and/or non-emergency vehicledestination location data.

The systems and methods may further generate insurance-related databased upon, for example, emergency vehicle warning data, alternatevehicle routing data, and/or telematics data. The insurance-related datamay be representative of a lower insurance risk for an emergency vehiclethat includes an emergency vehicle device (e.g., emergency vehicledevice 205 of FIG. 2) compared to an emergency vehicle that does notinclude an emergency vehicle device 205. Furthermore, theinsurance-related data may be representative of a lower insurance riskfor a non-emergency vehicle that includes a non-emergency vehicle device(e.g., non-emergency vehicle device 265 of FIG. 2) compared to anon-emergency vehicle that does not include a non-emergency vehicledevice 205.

While the systems and methods of the present disclosure may generate andtransmit insurance-related data, which may include or be representativeof personal information and individual insurance policy information, thesystems and methods may include an “opt-in” feature that enables anygiven individual to select a content of any insurance policy relateddata. Furthermore, the systems and methods may automatically exclude allpersonal information and individual insurance policy information fromthe insurance-related data. For example, the systems and methods maygenerate insurance-related data that only includes an indication as towhether any given vehicle is equipped with an emergency vehicle warningdevice, such as to avoid transmitting or broadcasting personal orsensitive information unnecessarily.

It should be noted that currently, the National Weather Service is ableto send automatic alerts to, for example, cellular telephones to warnthe associated users of bad weather. These are sent automatically (nosubscription necessary) to “WEA-capable” phones (see, e.g.,http://www.noaa.gov/features/03_protecting/wireless_emergency_alerts.html).In one embodiment, a method similar to the National Weather Service maybe developed that would alert drivers in the path of EMS vehicles. Froman insurance perspective this system may reduce EMS/auto collisionaccidents, speed response time (e.g., fire trucks) which might reducefire losses, and faster response to auto accidents may reduceinjuries/save lives.

The present embodiments may also be used to notify drivers of tornados,hail storms, wind storms, rain, snow, heavy rain, heavy snow, wind,thunder storms, hurricanes, etc. in the vicinity of their vehicle and/oralong their route of travel. For instance, based upon GPS coordinatecomparison of a weather event and a traveling vehicle, a warning oralternate route to a driver may be provided (such as “Tornado Watch 15miles ahead, take alternate route, and seek shelter”; “Heavy Snow 30miles ahead, take alternate route”; “Thunders storms 5 miles aheadmoving East at 40 mph”; etc.

In certain aspects, the present embodiment may provide benefits toinsurance providers and insurance customers, such as to lessen theamount of damage that results from insurance-related events, such ashouse fires, vehicle accidents, home breakins, etc. Emergency respondersmay arrive on the scene of an insurance-related event quicker, and thustaken prompt action to lessen damage. The functionality described hereinmay be used to adjust or update insurance policies, such as adjust orupdate insurance premiums, rates, discounts, risk levels, etc.associated with auto, home, health, life, personal, personal articles,and/or other types of insurance based upon an insured having one or moreof the functionalities or capabilities discussed herein.

In one embodiment, an autonomous vehicle may be in direct or indirectwireless communication or data transmission with a smart emergencyvehicle. As the smart emergency vehicle travels to the scene of aninsurance-related event, such as a vehicle accident, fire, medicalemergency, or police emergency, the smart emergency vehicle maybroadcast or transmit (via a vehicle-mounted transceiver) certaininformation to vehicles directly in front of it and/or along its routeof travel. The information transmitted may include a position,destination, speed, heading, route, GPS location, and/or otherinformation associated with the smart emergency vehicle. A vehiclecontroller (having an associated transceiver) of a non-emergency vehiclemay receive that information and compare it with the position,destination, speed, heading, route, GPS location, and/or otherinformation of the non-emergency vehicle.

Based upon the comparison, the vehicle controller may generate anaudible or visual alert announcing the presence or route of theemergency vehicle, and/or provide recommendations and/or alternateroutes that may avoid the emergency vehicle (such as “Move over to theshoulder”; “Turn right and take alternate route along Main St. todestination”; “Pull off to the side street”; “Pull into the shoppingmall parking mall to let emergency vehicles pass,” etc.) The visual oraudible alert may get the drivers attention.

Also, if an emergency vehicle alert or other alert is received, thevehicle may automatically turn off the vehicle's entertainment system(e.g., loud music) and then provide recommendations or directions to thedriver. If the non-emergency vehicle receiving the emergency vehicleinformation via the broadcast is a smart and/or autonomous vehicle, thenon-emergency vehicle may automatically re-route itself (such asdetermine an alternate route to the destination and/or pull off to theside of the road) to avoid the path of the emergency vehicle and/oralleviate an amount that the non-emergency vehicle interferes with thepath of the emergency vehicle.

As noted, the present embodiments may facilitate getting non-emergencyvehicles out of the way on emergency vehicles. The present embodimentsmay alert drivers not to head/drive in the direction of emergencyvehicles, and/or may provide intelligent routing based upon wirelesscommunication and/or data transmission indicating the real-time orcurrent location of emergency vehicles, accident scenes, house fires,hospital locations, police scenes, etc. In some aspects, a virtualnavigation map may pop up on a mobile device, smart vehicle displayscreen, or vehicle-mounted navigation unit to provide just-in-timevehicle re-routing to get around or avoid the route of emergencyvehicles, vehicle accidents, etc.

Emergency vehicles may include transponders or transceivers thatbroadcast to cell towers, mobile devices, and/or vehicles. Thetransponders or transceivers may also broadcast data to smart vehiclesand/or autonomous vehicles, such as via P2P wireless communicationand/or vehicle-to-vehicle (V2V) wireless communication. Warnings may begenerated at the emergency vehicles themselves, and/or at processorsassociated with the cell towers, mobile devices, vehicles, smartvehicles, and/or autonomous vehicles based upon the data received fromthe emergency vehicles (such as data associated with current vehiclelocation, route, destination, etc.). The warnings may includeinformation about vehicle accidents, accident locations, suggestalternate routing, and/or provide other forewarnings. Automation ofcommon procedures, triggered by emergency vehicle warnings, may reducecomputer processing times, memory requirements and/or relatedfacilities. Using the methods and systems, insurance customers may beautomatically warned of emergency vehicle(s) in the proximity of thecustomer's location, focused on relevant information to the emergencyvehicle(s), and/or provided with reduced risk to the insurance customerand reductions in related insurance agreement information.

Exemplary System for Generating Emergency Vehicle Warning Data and/orInsurance-Related Data

With reference to FIG. 1, a system for generating emergency vehiclewarning data and/or insurance-related data 100 may include a remotelocation 105, a communication system 110, at least one emergency vehicle120, and/or at least one non-emergency vehicle 130. While only oneemergency vehicle 120 and only one non-emergency vehicle 130 aredepicted in FIG. 1, it should be understood that any number of emergencyvehicles 120 and only one non-emergency vehicles 130 may be included ina system for generating emergency vehicle warning data 100. Theemergency vehicles 120 and non-emergency vehicle 130 may be in directwireless communication or data transmission with one another, such asvia peer-to-peer (P2P) communication, and/or in indirect wirelesscommunication or data transmission with one another, such as by using acell tower or remote server/processor associated with a remote location105 as a relay.

In any event, an emergency call may be received by, for example, adispatcher located, for example, at the remote location 105. In responseto the emergency call, the dispatcher may assign a particular emergencyresponse vehicle to respond to the emergency call. In conjunction withassigning the emergency vehicle, the dispatcher may enter emergencyvehicle data into, for example, a remote emergency management servicesdevice (e.g., remote EMS computing device 210 of FIG. 2). The emergencyvehicle data may be representative of, for example, an emergency vehicleorigination location data, an emergency vehicle route data, and/or anemergency vehicle destination location data.

The dispatcher may transmit the emergency vehicle data to the emergencyvehicle 120 via a first communication link 115 and a secondcommunication link 125. The first communication link 115 and the secondcommunication link 125 may combine to define, for example, apeer-to-peer communication link. Alternatively, the first communicationlink 115 and the second communication link 125 may combine with thecommunication system 110 to define, for example, a cellular telephonenetwork.

In response to receiving the emergency vehicle data from the remotelocation, the emergency vehicle 120 may begin transmitting emergencyvehicle data. For example, the emergency vehicle 120 may transmitemergency vehicle data back to the remote location 105, via the firstcommunication link 115 and the second communication link 125, and/or tothe non-emergency vehicle 130 via the second communication link 125 anda third communication link 135. Similar, to the first communication link115 and the second communication link 125, the second communication link125 and the third communication link 135 may combine to define, forexample, a peer-to-peer communication link. Alternatively, the secondcommunication link 125 and the third communication link 135 may combinewith the communication system 110 to define, for example, a cellulartelephone network.

As an alternative to the remote location 105 and/or the emergencyvehicle 120 transmitting emergency vehicle data, emergency vehiclewarning data may be generated, using a processor of a computing device(e.g., processor 275 or processor 250, respectively), based upon theemergency vehicle data, and the remote location 105 and/or the emergencyvehicle 120 may transmit/receive the emergency vehicle warning data.

In an additional embodiment, the emergency vehicle 120 may wirelesslycommunicate current location, route, speed, destination, type ofemergency, and/or other information to a smart roadside sign. The smartroadside sign may display messages to vehicles (such as non-emergencyvehicles 130) passing by, such as displaying road or travel conditionsthat a non-emergency vehicle 130 is approaching, and/or the status orroute of an emergency vehicle 120 approaching or otherwise in thevicinity. The smart roadside sign may display or otherwise indicateradio stations that travelers may tune their radios to in order to hearfurther updates, and/or current locations of emergencies (such asvehicle accidents) and/or emergency vehicles 120. Additionally oralternatively, the smart roadside sign may wirelessly communicateemergency vehicle 120 information (such as the information receiveddirectly or indirectly from an emergency vehicle 120) directly orindirectly to non-emergency vehicles 130 or mobile devices of travelersto enhance road safety and awareness of emergency vehicles 120.

Exemplary System for Generating Emergency Vehicle Warning Data and/orInsurance-Related Data

Turning to FIG. 2, a computer system for generating emergency vehiclewarning data 200 may include an emergency vehicle device 205 and anon-emergency vehicle device 265 in communication with a remoteemergency management services computer device 210 via a communicationsnetwork 215. The computer system 200 may implement communicationsbetween the emergency vehicle device 205, the non-emergency vehicledevice 265, and the remote emergency management services device 210 toprovide, for example, emergency vehicle warning data to an emergencymanagement services related database 260. For example, the computersystem 200 may acquire emergency vehicle data from, for example, a userof an emergency vehicle device 205 and/or non-emergency vehicle datafrom, for example, a user of a non-emergency vehicle device 265. Asdescribed in detail herein, the computer system 200 may automaticallygenerate emergency vehicle warning data based upon, for example,emergency vehicle data and/or non-emergency vehicle data.

For clarity, only one emergency vehicle device 205, one non-emergencyvehicle device 265, and one remote emergency management services device210 are depicted in FIG. 2. While FIG. 2 depicts only one emergencyvehicle device 205, one non-emergency vehicle device 265, and one remoteemergency management services device 210, it should be understood thatany number of emergency vehicle devices 205, any number of non-emergencyvehicle devices 265, and any number of remote emergency managementservices computing devices may be supported, and that each emergencyvehicle device 205, each non-emergency vehicle device 265, and eachremote emergency management services computing device 210 may be anyappropriate computing device, such as a mobile telephone, a personaldata assistant, a tablet or a lap-top computer.

An emergency vehicle device 205 may include a memory 220 and a processor225 for storing and executing, respectively, a module 221. The module221, stored in the memory 220 as a set of computer-readableinstructions, may be related to an application for generating emergencyvehicle warning data, and/or insurance-related data, based uponemergency vehicle data and/or non-emergency vehicle data that, whenexecuted on a processor 225, causes data representative of emergencyvehicle warning data and/or insurance-related data based upon emergencyvehicle data and/or non-emergency vehicle data to be stored in thememory 220. As described in detail herein, the module 221 may facilitateinteraction between an associated emergency vehicle device 205, anon-emergency vehicle device 265, and/or a remote emergency managementservices computing device 210. The processor 225, further executing themodule 221, may facilitate communications between a remote emergencymanagement services computing device 210, an emergency vehicle device205, and/or a non-emergency vehicle device 265 via a network interface240 and a network 215.

An emergency vehicle device 205 may include a global positioning system(GPS) 227. An emergency vehicle device 205 may include a display device235 which may be any type of electronic display device such as a liquidcrystal display (LCD), a light emitting diode (LED) display, a plasmadisplay, a cathode ray tube (CRT) display, or any other type of known orsuitable electronic display. A display device 235 may exhibit a displaywhich depicts a user interface for configuring an emergency vehicledevice 205 to communicate with a non-emergency vehicle device 265 and/ora remote emergency management services computing device 210. Anemergency vehicle device 205 may include a user input device 230, suchas a touch input/keyboard/pointing device (e.g., a mouse) that providesa mechanism for a user of the emergency vehicle device 205 to launch anemergency vehicle device insurance application and, for example, tointeract with a system for generating emergency vehicle warning data,and/or insurance-related data, based upon emergency vehicle data and/ornon-emergency vehicle data. The user input device 230 may be configuredas an integral part of a display device 235, such as a touch screendisplay device.

The network interface 240 may be configured to facilitate communicationsbetween an emergency vehicle device 205, a non-emergency vehicle device265, and/or a remote emergency management services computing device 210via any wireless communication network 215, including for example apeer-to-peer communications link, wireless LAN, MAN or WAN, WiFi, theInternet, or any combination thereof. Moreover, an emergency vehicledevice 205 may be communicatively connected to a remote emergencymanagement services device 210 via any suitable communication system,such as via any publicly available or privately owned communicationnetwork, including those that use wireless communication structures,such as wireless communication networks, including for example, apeer-to-peer communications link, wireless LANs and WANs, satellite andcellular telephone communication systems, etc. An emergency vehicledevice 205 may cause, for example, emergency vehicle data and/oremergency vehicle warning data to be transmitted to, and stored in, forexample, a remote emergency management services computing device 210memory 245 and/or a remote emergency management services relateddatabase 260.

A non-emergency vehicle device 265 may include a memory 270 and aprocessor 275 for storing and executing, respectively, a module 271. Themodule 271, stored in the memory 270 as a set of computer-readableinstructions, may be related to an application for generatingnon-emergency vehicle warning data, and/or insurance-related data, basedupon non-emergency vehicle data and/or emergency vehicle data that, whenexecuted on a processor 275, causes data representative of non-emergencyvehicle warning data and/or insurance-related data based upon emergencyvehicle data and/or non-emergency vehicle data to be stored in thememory 270. As described in detail herein, the module 271 may facilitateinteraction between an associated non-emergency vehicle device 265, anemergency vehicle device 205, and/or a remote emergency managementservices computing device 210. The processor 275, further executing themodule 271, may facilitate communications between a remote emergencymanagement services computing device 210, a non-emergency vehicle device265, and/or an emergency vehicle device 205 via a network interface 290and a network 215.

A non-emergency vehicle device 265 may include a global positioningsystem (GPS) 277. A non-emergency vehicle device 265 may include adisplay device 285 which may be any type of electronic display devicesuch as a liquid crystal display (LCD), a light emitting diode (LED)display, a plasma display, a cathode ray tube (CRT) display, or anyother type of known or suitable electronic display. A display device 285may exhibit a display which depicts a user interface for configuring anon-emergency vehicle device 265 to communicate with an emergencyvehicle device 205 and/or a remote emergency management servicescomputing device 210. A non-emergency vehicle device 265 may include auser input device 280, such as a touch input/keyboard/pointing device(e.g., a mouse) that provides a mechanism for a user of thenon-emergency vehicle device 265 to launch a non-emergency vehicledevice insurance application and, for example, to interact with a systemfor generating emergency vehicle warning data, and/or insurance-relateddata, based upon emergency vehicle data and/or non-emergency vehicledata. The user input device 280 may be configured as an integral part ofa display device 285, such as a touch screen display device.

The network interface 290 may be configured to facilitate communicationsbetween a non-emergency vehicle device 265, an emergency vehicle device205, and/or a remote emergency management services computing device 210via any wireless communication network 215, including for example apeer-to-peer communications link, wireless LAN, MAN or WAN, WiFi, theInternet, or any combination thereof. Moreover, a non-emergency vehicledevice 265 may be communicatively connected to a remote emergencymanagement services device 210 via any suitable communication system,such as via any publicly available or privately owned communicationnetwork, including those that use wireless communication structures,such as wireless communication networks, including for example, apeer-to-peer communications link, wireless LANs and WANs, satellite andcellular telephone communication systems, etc. A non-emergency vehicledevice 265 may cause, for example, non-emergency vehicle data to betransmitted to, and stored in, for example, a remote emergencymanagement services computing device 210 memory 245 and/or a remoteemergency management services related database 260.

A remote emergency management services computing device 210 may includea memory 245 and a processor 250 for storing and executing,respectively, a module 246. The module 246, stored in the memory 245 asa set of computer-readable instructions, may facilitate applicationsrelated to generating emergency vehicle warning data, and/orinsurance-related data, based upon emergency vehicle data and/ornon-emergency vehicle data. The module 246 may also facilitatecommunications between the remote emergency management servicescomputing device 210, an emergency vehicle device 205, and/or anon-emergency vehicle device 265 via a network interface 255 and thenetwork 215, and other functions and instructions.

A remote emergency management services device 210 may be communicativelycoupled to an emergency management services related database 260. Whilethe emergency management services related database 260 is shown in FIG.2 as being communicatively coupled to the remote emergency managementservices device 210, it should be understood that the emergencymanagement services related database 260 may be located within separateremote servers (or any other suitable computing devices) communicativelycoupled to the remote emergency management services computer device 210.Optionally, portions of emergency management services related database260 may be associated with memory modules that are separate from oneanother, such as a memory 220 of an emergency vehicle device 205 and/ora non-emergency vehicle device 265.

Exemplary Emergency Vehicle Device for Generating Emergency Vehicle Dataand/or Emergency Vehicle Warning Data

Turning to FIG. 3, an emergency vehicle device 300 may include a from/todata receiving module 310, a location data generation module 315, anemergency status data generation module 320, and/or a location andemergency status data transmission module 325 stored on, for example, amemory 305. The emergency vehicle device 300 may be similar to theemergency vehicle device 205 of FIG. 2, and/or may include additional,less, or alternate functionality, including that discussed elsewhereherein.

Exemplary Non-Emergency Vehicle Device for Generating Non-EmergencyVehicle Data and/or Emergency Vehicle Warning Data

Turning to FIG. 4, a non-emergency vehicle device 400 may include anemergency vehicle warning data receiving module 410, a warning and/oralternate driving route data generation module 415, and/or a warningand/or alternate driving route presentation module 420 stored on, forexample, a memory 405. The non-emergency vehicle device 400 may besimilar to the non-emergency vehicle device 265 of FIG. 2, and/or mayinclude additional, less, or alternate functionality, including thatdiscussed elsewhere herein.

Exemplary Remote Emergency Management Services Computing Device forGenerating Emergency Vehicle Warning Data, and Insurance-Related Data

With reference to FIG. 5, a remote emergency management servicescomputing device 500 may include an emergency call data receiving module510, an emergency vehicle dispatch and from/to data entering module 515,an effected geographic area determination module 520, an emergencyvehicle warning data generation module 525, an emergency vehicle warningdata transmission module 530, and/or an insurance-related datageneration module 535 stored on, for example, a memory 505. The remoteemergency management services computing device 500 may be similar to,for example, the remote emergency management services computing device210 of FIG. 2, and/or may include additional, less, or alternatefunctionality, including that discussed elsewhere herein.

Exemplary Method for Generating Emergency Vehicle Data and/or EmergencyVehicle Warning Data

Turning to FIG. 6, a method of automatically generating emergencyvehicle data 600 may be implemented by a processor (e.g., processor 225of emergency vehicle device 205 of FIG. 2) executing, for example,modules 310-320 of FIG. 3. In particular, processor 225 may execute thefrom/to data receiving module 310 to cause the processor 225 to receiveto/from data from, for example, a processor of a remote emergencymanagement services computer (e.g., processor 250) (block 605). Theprocessor 225 may execute the location data generation module 315 tocause the processor 225 to generate emergency vehicle location databased upon, for example, a global positioning system (GPS) 227 signal(block 610). The processor 225 may execute the emergency status datageneration module 320 to cause the processor 225 to generate emergencystatus data (block 615). The emergency status data may be indicative ofwhether an associated emergency vehicle is, for example, currently inmotion, or is currently stationary.

The processor 225 may execute the location and emergency status datatransmission module 325 to cause the processor 225 to transmit emergencyvehicle data to, for example, a processor of a remote emergencymanagement services computing device (e.g., processor 250) and/or to aprocessor of a non-emergency vehicle device (e.g., processor 275) (block620). The emergency vehicle data may be based upon, for example, thelocation data and/or the emergency status data. For example, theemergency vehicle data may be representative of an emergency vehicleorigination location, an emergency vehicle current location, anemergency vehicle route, and/or an emergency vehicle destinationlocation.

Additionally, or alternatively, the processor 225 may execute anemergency vehicle warning data generation module 525 to generateemergency vehicle warning data (and/or alternate routing information)based upon, for example, emergency vehicle data and/or non-emergencyvehicle data. When the processor 225 generates emergency vehicle warningdata (and/or alternate routing information), the processor 225 maytransmit the emergency vehicle warning data in addition to, or in lieuof, the emergency vehicle data, to, for example, a processor of a remoteemergency management services computing device (e.g., processor 250)and/or to a processor of a non-emergency vehicle device (e.g., processor275) (block 620). The method may include additional, fewer, or alternateactions, including those discussed elsewhere herein.

Exemplary Method for Generating Non-Emergency Vehicle Data and/orEmergency Vehicle Warning Data

With reference to FIG. 7, a method of automatically generatingnon-emergency vehicle data 500 may be implemented by a processor (e.g.,processor 275 of non-emergency vehicle device 265 of FIG. 2) executing,for example, modules 410-420 of FIG. 4. In particular, processor 275 mayexecute an emergency vehicle warning data receiving module 410 toreceive emergency vehicle warning data from, for example, a processor ofa remote emergency management services computing device (e.g., processor250) and/or a processor of an emergency vehicle device (e.g., processor225) (block 705). The processor 275 may execute a warning and/oralternate driving route data generation module 415 to cause theprocessor 275 to generate warning data and/or alternate driving routedata based upon the emergency vehicle warning data (block 710).

The processor 275 may execute a warning and/or alternate driving routepresentation module 420 to cause the processor 275 to generate apresentation of a warning based upon the warning data and/or apresentation of an alternate driving route based upon the alternatedriving route data (block 715). The presentation of the warning may be,for example, a visual alarm, a motion alarm (e.g., vibration of a seator steering wheel) and/or an audible alarm, and may be indicative of anemergency vehicle being in a geographic area of the non-emergencyvehicle.

The presentation of the alternate driving route may be, for example, avisual presentation and/or an audible presentation, and may beindicative of a driving route that will avoid intersection with anemergency vehicle. The processor 275 may execute a module (e.g., amodule location data generation module 315) to cause the processor 275to generate non-emergency vehicle location data based, for example, uponan output of a sensor (e.g., GPS 277 of FIG. 2). The method may includeadditional, fewer, or alternate actions, including those discussedelsewhere herein.

Exemplary Method for Generating Emergency Vehicle Warning Data and/orInsurance-Related Data

Turning to FIG. 8, a method of automatically generating emergencyvehicle warning data and/or insurance-related data 800 may beimplemented by a processor (e.g., processor 250 of remote emergencymanagement services computing device 210 of FIG. 2) executing, forexample, modules 510-535 of FIG. 5. In particular, the processor 250 mayexecute the emergency call data receiving module 510 to cause theprocessor 250 to receive emergency call data (block 805). For example,the emergency call data may be automatically entered into the remoteemergency management services computing device 210 when the individualseeking emergency services calls into a remote location (e.g., remotelocation) and enters information via, for example, a telephone. Theemergency call data may be representative of information received by,for example, an emergency management services dispatcher from anindividual seeking emergency services (e.g., medical, fire, police,etc.). Alternatively, the processor 250 may execute an emergencymanagement system vehicle dispatch and from/to data entering module 520such that a dispatcher may enter the emergency call data into, forexample, a remote emergency management services computing device (e.g.,remote emergency management services computing device 210 of FIG. 2)via, for example, a user input device (e.g., a keyboard, a touch screen,a voice actuated system, etc.) (block 810).

The processor 250 may execute the effected geographic area determinationmodule 520 to cause the processor 250 to generate effected geographicarea data based upon the emergency call data (block 815). The effectedgeographic area data may be representative of a geographic area in whichan emergency vehicle will travel, an emergency vehicle originationlocation, an emergency vehicle driving route, and/or an emergencyvehicle destination location. The processor 250 may execute theemergency vehicle warning data generation module 525 to cause theprocessor 250 to generate emergency vehicle warning data based uponemergency vehicle data and/or non-emergency vehicle data (block 820).The processor 250 may execute the emergency management services datatransmission module 530 to cause the processor 250 to transmit emergencyvehicle data and/or emergency vehicle warning data to a processor of anon-emergency vehicle device (e.g., processor 275 of FIG. 2) and/or aprocessor of an emergency vehicle device (e.g., processor 225 of FIG. 2)(block 825).

The processor 250 may execute an insurance-related data generationmodule 535 to cause the processor 250 to generate insurance-related databased upon the emergency vehicle data, the non-emergency vehicle data,and/or the emergency vehicle warning data (block 830). Theinsurance-related data may be, for example, representative of whether anemergency vehicle includes an emergency vehicle device (e.g., emergencyvehicle device 205 of FIG. 2) and/or a non-emergency vehicle includes anon-emergency vehicle device (e.g., non-emergency vehicle device 265 ofFIG. 2).

In particular, the insurance-related data may be representative of alower insurance risk for an emergency vehicle that includes an emergencyvehicle device 205 compared to an emergency vehicle that does notinclude an emergency vehicle device 205. Furthermore, theinsurance-related data may be representative of a lower insurance riskfor a non-emergency vehicle that includes a non-emergency vehicle device265 compared to a non-emergency vehicle that does not include anon-emergency vehicle device 205. The method may include additional,less, or alternate functionality, including that discussed elsewhereherein.

Exemplary Computer Implemented Method

In one aspect, a computer implemented method for generating datarepresentative of an emergency vehicle warning may be provided. Themethod may include (1) receiving, at a processor of a computing device,emergency vehicle data, in response to the processor executing anemergency vehicle data receiving module. The emergency vehicle data maybe representative of at least one of: emergency vehicle originationlocation data, emergency vehicle current location data, emergencyvehicle route data, and emergency vehicle destination location data. Themethod may also include (2) receiving, at a processor of a computingdevice, non-emergency vehicle data, in response to the processorexecuting a non-emergency vehicle data receiving module. Thenon-emergency vehicle data may be representative of at least one of:non-emergency vehicle origination location data, non-emergency vehiclecurrent location data, non-emergency vehicle route data, andnon-emergency vehicle destination location data. The method may furtherinclude (3) generating, using a processor of a computing device,emergency vehicle warning data, based upon the emergency vehicle dataand the non-emergency vehicle data, in response to the processorexecuting an emergency vehicle warning data generation module.

The method may yet further include (4) generating, using a processor ofa computing device, insurance-related data, based upon the emergencyvehicle warning data, in response to the processor executing aninsurance-related data generation module. The insurance-related data maybe representative of an insurance risk associated with a non-emergencyvehicle, and the insurance risk may be lower for a non-emergency vehiclethat is equipped with an emergency vehicle warning data receivingdevice. The insurance-related data may be representative of an insurancerisk associated with an emergency vehicle, and an insurance risk may belower for an emergency vehicle that is equipped with an emergencyvehicle warning data generation and receiving device.

The method may include (5) transmitting, using a processor of acomputing device, emergency vehicle warning data, to a non-emergencyvehicle, in response to the processor executing an emergency vehiclewarning data transmission module. The method may include (6)transmitting, using a processor of a computing device, emergency vehicledata, from an emergency vehicle to a non-emergency vehicle, in responseto the processor executing an emergency vehicle data transmissionmodule. The method may include additional, less, or alternate actions,including that discussed elsewhere herein.

Exemplary System

A system for generating emergency vehicle warning data (and/or alternaterouting data) may be provided. The system may include an emergencyvehicle data receiving module stored on a memory that, when executed bya processor of a computing device, may cause the processor to receiveemergency vehicle data. The emergency vehicle data may be representativeof at least one of: emergency vehicle origination location data,emergency vehicle current location data, emergency vehicle route data,and/or emergency vehicle destination location data. The system may alsoinclude a non-emergency vehicle data receiving module stored on a memorythat, when executed by a processor of a computing device, may cause theprocessor to receive non-emergency vehicle data. The non-emergencyvehicle data may be representative of at least one of: non-emergencyvehicle origination location data, non-emergency vehicle currentlocation data, non-emergency vehicle route data, and/or non-emergencyvehicle destination location data. The system may further include anemergency vehicle warning data (and/or alternate routing data)generation module stored on a memory that, when executed by a processorof a computing device, may cause the processor to generate emergencyvehicle warning data (and/or alternate routing data), based upon theemergency vehicle data and the non-emergency vehicle data. The systemmay include additional, less, or alternate functionality, including thatdiscussed elsewhere herein.

For instance, the system may include an insurance-related datageneration module stored on a memory that, when executed by a processorof a computing device, may cause the processor to generateinsurance-related data, based upon the emergency vehicle warning data(and/or alternate routing data). The insurance-related data may berepresentative of an insurance risk associated with a non-emergencyvehicle, and the insurance risk may be lower for a non-emergency vehiclethat is equipped with an emergency vehicle warning data (and/oralternate routing data) receiving device, and/or the insurance-relateddata may be representative of an insurance risk associated with anemergency vehicle, and the insurance risk may be lower for an emergencyvehicle that is equipped with an emergency vehicle warning data (and/oralternate routing data) generation and receiving device.

The system may also include an emergency vehicle data transmissionmodule stored on a memory that, when executed by a processor of acomputing device, may cause the processor to transmit emergency vehicledata (and/or associated alternate routing data) from an emergencyvehicle to a non-emergency vehicle via a point-to-point communicationlink.

The system may also include an emergency vehicle warning data (and/oralternate routing data) transmission module stored on a memory that,when executed by a processor of a computing device, may cause theprocessor to transmit emergency vehicle warning data (and/or alternaterouting data) from a processor of a remote emergency management servicesdevice to a non-emergency vehicle via a cellular telephone network.

The emergency vehicle data receiving module, the non-emergency vehicledata receiving module, and the emergency vehicle warning data generationmodule may be executed by a processor of a remote emergency managementservices device, and the remote emergency management services device mayinclude an insurance-related data generation module stored on a memorythat, when executed by the processor of the remote emergency managementservices device, may cause the processor to generate insurance-relateddata, based upon the emergency vehicle warning data.

Exemplary Computer-Readable Instructions

A non-transitory computer-readable medium storing instructions that,when executed by a processor of a computing device, may cause theprocessor to automatically generate personal article insurance data mayinclude an emergency vehicle data receiving module that, when executedby a processor of a computing device, may cause the processor to receiveemergency vehicle data. The emergency vehicle data may be representativeof at least one of: emergency vehicle origination location data,emergency vehicle current location data, emergency vehicle route data,and/or emergency vehicle destination location data.

The non-transitory computer-readable medium may also include anon-emergency vehicle data receiving module that, when executed by aprocessor of a computing device, may cause the processor to receivenon-emergency vehicle data. The non-emergency vehicle data may berepresentative of at least one of: non-emergency vehicle originationlocation data, non-emergency vehicle current location data,non-emergency vehicle route data, and/or non-emergency vehicledestination location data.

The non-transitory computer-readable medium may further include anemergency vehicle warning data generation module that, when executed bya processor of a computing device, may cause the processor to generateemergency vehicle warning data (and/or alternate routing information),based upon the emergency vehicle data and the non-emergency vehicledata. The non-transitory computer-readable medium may include anemergency vehicle warning (and/or alternate routing) presentation modulethat, when executed by a processor of a computing device, may cause theprocessor to generate an emergency vehicle warning and/or alternaterouting) presentation based upon the emergency vehicle warning data. Thenon-transitory computer-readable medium may include an insurance-relateddata generation module that, when executed by a processor of a computingdevice, may cause the processor to generate insurance-related data basedupon the emergency vehicle warning data.

The non-transitory computer-readable medium may include an emergencyvehicle data transmission module that, when executed by a processor of acomputing device, may cause the processor to transmit emergency vehicledata from a first emergency vehicle to a second emergency vehicle. Thenon-transitory computer-readable medium may include an emergency vehiclewarning data transmission module that, when executed by a processor of acomputing device, may cause the processor to transmit emergency vehiclewarning data from the processor to an emergency vehicle.

Additionally or alternatively, the non-transitory computer-readablemedium may include a non-emergency vehicle alternate route presentationmodule that, when executed by a processor of a computing device, maycause the processor to generate a non-emergency vehicle alternate routepresentation based upon the emergency vehicle warning data.

The non-transitory computer-readable medium may include an effectedgeographic area data generation module that, when executed by aprocessor of a computing device, may cause the processor to generateeffected geographic area data based upon the emergency vehicle data,and/or an emergency vehicle data warning transmission module that, whenexecuted by a processor of a computing device, may cause the processorto transmit emergency vehicle warning data and/or alternate routing datato non-emergency vehicles based upon the effected geographic area data.

The non-transitory computer-readable medium may include an emergencyvehicle data transmission module that, when executed by a processor of acomputing device, may cause the processor to transmit emergency vehicledata to a non-emergency vehicle. The non-transitory computer-readablemedium may include an emergency vehicle warning data transmission modulethat, when executed by a processor of a computing device, may cause theprocessor to transmit emergency vehicle warning data from the processorto a non-emergency vehicle.

Exemplary Computer Implemented Method

In one aspect, a computer implemented method for generating datarepresentative of an emergency vehicle warning and/or alternate vehicleroute may be provided. The method may include (1) receiving, generating,or collecting, via or at one or more processors (such as processorsassociated with an emergency vehicle, non-emergency vehicle, and/orremote servers), emergency vehicle data via wireless communicationand/or data transmission, wherein the emergency vehicle data isrepresentative of: emergency vehicle origination location data,emergency vehicle current location data, emergency vehicle route data,emergency vehicle destination location data, and/or type of emergency;(2) receiving, generating, or collecting, via or at the one or moreprocessors (such as processors associated with an emergency vehicle,non-emergency vehicle, and/or remote servers), non-emergency vehicledata, wherein the non-emergency vehicle data is representative of:non-emergency vehicle origination location data, non-emergency vehiclecurrent location data, non-emergency vehicle route data, and/ornon-emergency vehicle destination location data; (3) receiving orgenerating, via or at the one or more processors (such as processorsassociated with an emergency vehicle, non-emergency vehicle, and/orremote servers), emergency vehicle warning data and/or alternate vehicleroute data based upon computer analysis and/or comparison of theemergency and non-emergency vehicle data, the alternate vehicle route(i) directing the non-emergency vehicle out of the way of the emergencyvehicle, (ii) avoids the route of the emergency vehicle, and/or (iii)alleviates an amount that the non-emergency vehicle interferes with aroute of the emergency vehicle; and/or (4) causing, via or at the one ormore processors (such as processors associated with an emergencyvehicle, non-emergency vehicle, and/or remote servers), the emergencyvehicle warning data and/or alternate vehicle route data, to bepresented or provided to a driver of the non-emergency vehicle tofacilitate alleviating potential vehicle accidents between emergencyresponse and non-emergency response vehicles, and/or shorteningemergency response times for emergency vehicles. The method may includeadditional, less, or alternate actions, including those discussedelsewhere herein, and/or the method may be implemented via a computersystem, communication network, one or more processors, and/orcomputer-executable instructions stored on non-transitory storage mediaor computer-readable medium.

For instance, the method may include generating, via the one or moreprocessors, insurance-related data for the driver of the non-emergencyvehicle based upon the driver following recommendations associated withemergency vehicle warnings and/or alternate vehicle routing to avoidemergency vehicles. The insurance-related data may be representative ofan insurance risk associated with a non-emergency vehicle, and theinsurance risk may be lower for a non-emergency vehicle that is equippedwith an emergency vehicle warning data receiving device. Theinsurance-related data may be representative of an insurance riskassociated with an emergency vehicle, and the insurance risk may belower for an emergency vehicle that is equipped with an emergencyvehicle warning data generation, transmitting, and/or receiving device.

The method may include transmitting, via the one or more processors,emergency vehicle warning data and/or alternate vehicle route data toother vehicles or processors. The one or more processors may be mountedon an autonomous or smart vehicle, and the autonomous or smart vehicleautomatically may direct or drive itself to take an alternate vehicleroute and/or take self-driving actions that allow the autonomous orsmart vehicle avoid the emergency vehicle and/or a route of theemergency vehicle.

Exemplary Vehicle-Mounted Systems

In one aspect, a vehicle-mounted system of a vehicle for generatingemergency vehicle warning data and/or alternate route data may beprovided. The system may include one or more processors configured to:(1) receive emergency vehicle data, wherein the emergency vehicle datais representative of: emergency vehicle origination location data,emergency vehicle current location data, emergency vehicle route data,emergency vehicle destination location data, and/or alternate routing,(2) collect non-emergency vehicle data, the non-emergency vehicle dataassociated with the vehicle and being generated by one or morevehicle-mounted sensors or processors, the non-emergency vehicle data isrepresentative: non-emergency vehicle origination location data,non-emergency vehicle current location data, non-emergency vehicle routedata, and/or non-emergency vehicle destination location data; (3)generate an emergency vehicle warning and/or alternate route based uponcomputer analysis and/or comparison of the emergency vehicle data andthe non-emergency vehicle data; and/or (4) present the emergency vehiclewarning and/or alternate route to the driver of the vehicle such thatdriver of the vehicle, or the vehicle itself, may avoid may avoid theroute of the emergency vehicle and/or to facilitate shortening responsetime for emergency vehicles.

The system may include additional, less, or alternate functionality,including that discussed elsewhere herein. For instance, the vehicle maybe an autonomous vehicle that automatically avoids the route of theemergency vehicle based upon computer comparison or analysis of theemergency and non-emergency vehicle data.

The system may further include an insurance-related data generationmodule stored on a memory that, when executed by a processor of acomputing device, causes the processor to generate insurance-relateddata, based upon the emergency vehicle warning and/or alternate routedata. The insurance-related data may be representative of an insurancerisk associated with a non-emergency vehicle, and/or the insurance riskmay be lower for a non-emergency vehicle that is equipped with anemergency vehicle warning data receiving device. Additionally oralternatively, the insurance-related data may be representative of aninsurance risk associated with an emergency vehicle, and/or theinsurance risk may be lower for an emergency vehicle that is equippedwith an emergency vehicle warning data generation and receiving device.

Exemplary Non-Emergency Vehicle Implemented Method

In one aspect, a computer implemented method for generating datarepresentative of an emergency vehicle warning and/or alternate vehicleroute may be provided and/or may be performed by a non-emergencyvehicle. The method may include (1) receiving, via or at one or moreprocessors associated with a non-emergency vehicle, emergency vehicledata via wireless communication and/or data transmission, wherein theemergency vehicle data is representative of: emergency vehicleorigination, current location, current speed, current heading, currentroute, and/or current destination, and/or type of emergency; (2)generating or collecting, via or at the one or more processorsassociated with the non-emergency vehicle, non-emergency vehicle data(such as from one or more vehicle-mounted sensors), wherein thenon-emergency vehicle data is representative of: non-emergency vehicleorigination, current location, current speed, current heading, currentroute, and/or current destination: (3) generating, via or at the one ormore processors associated with the non-emergency vehicle, emergencyvehicle warning data and/or alternate vehicle route data based uponcomputer analysis and/or comparison of the emergency and non-emergencyvehicle data that is performed by the one or more processors associatedwith the non-emergency vehicle, the alternate vehicle route (i)directing the non-emergency vehicle out of the way of the emergencyvehicle, (ii) avoids the route of the emergency vehicle, and/or (iii)alleviates an amount that the non-emergency vehicle interferes with aroute of the emergency vehicle; and/or (4) causing, via or at the one ormore processors associated with the non-emergency vehicle, the emergencyvehicle warning data and/or alternate vehicle route data, to bepresented or provided to a driver of the non-emergency vehicle tofacilitate alleviating potential vehicle accidents between emergencyresponse and non-emergency response vehicles, and/or shorteningemergency response times for emergency vehicles.

The method may further include adjusting an insurance policy, premium,rate, or discount for the non-emergency vehicle based upon thenon-emergency vehicle having the vehicle warning and/or alternatevehicle route generation functionality. The method may includeadditional, less, or alternate functionality, including that discussedelsewhere herein, and/or the method may be implemented via a computersystem, communication network, one or more processors, and/orcomputer-executable instructions stored on non-transitory storage mediaor computer-readable medium.

Exemplary Autonomous Vehicle Implemented Method

In one another aspect, a computer implemented method for generating datarepresentative of an emergency response vehicle warning and/or alternatevehicle route may be provided. The method may include (1) receiving, viaor at one or more processors mounted on an autonomous, non-emergencyresponse vehicle, emergency response vehicle data via wirelesscommunication and/or data transmission, wherein the emergency responsevehicle data is representative of: emergency response vehicle origin,current location, current speed, current heading, current route, and/orcurrent destination, and/or type of emergency, such as a vehicleaccident or weather event; (2) generating or collecting, via or at theone or more processors mounted on the autonomous, non-emergency responsevehicle, non-emergency response vehicle data associated with theautonomous, non-emergency response vehicle, wherein the non-emergencyresponse vehicle data is representative of: the autonomous,non-emergency response vehicle origination, current location, currentspeed, current heading, current route, and/or current destination; (3)generating, via or at the one or more processors mounted on theautonomous, non-emergency response vehicle, emergency response vehiclewarning data and/or alternate vehicle route data based upon computeranalysis and/or comparison of the emergency response and non-emergencyresponse vehicle data that is performed by the one or more processorsmounted on the autonomous, non-emergency response vehicle, the alternatevehicle route (i) directing the autonomous, non-emergency responsevehicle out of the way of the emergency response vehicle, (ii) avoidsthe route of the emergency response vehicle, and/or (iii) alleviates anamount that the autonomous, non-emergency response vehicle interfereswith a route of the emergency response vehicle; and/or (4) causing, viaor at the one or more processors mounted on the autonomous,non-emergency response vehicle, the autonomous, non-emergency responsevehicle to automatically take the alternate route and/or present theemergency response vehicle warning to a passenger within the autonomous,non-emergency response vehicle to facilitate alleviating potentialvehicle accidents between emergency response and non-emergency responsevehicles, and/or shortening emergency response times for emergencyresponse vehicles.

The method may further include adjusting an insurance policy, premium,rate, or discount for the autonomous, non-emergency response vehiclebased upon the autonomous, non-emergency response vehicle having thevehicle warning and/or alternate vehicle route generation functionality.The method may include additional, less, or alternate functionality,including that discussed elsewhere herein, and/or the method may beimplemented via a computer system, communication network, one or moreprocessors, and/or computer-executable instructions stored onnon-transitory storage media or computer-readable medium.

Exemplary Emergency Response Vehicle Implemented Method

In one aspect, a computer implemented method for generating datarepresentative of an emergency response vehicle warning and/or alternatevehicle route may be provided. The method may include (1) generating orcollecting, via or at one or more processors mounted on an emergencyresponse vehicle, emergency response vehicle data (such as fromvehicle-mounted sensors), wherein the emergency response vehicle data isrepresentative of: emergency response vehicle origin, current location,current speed, current heading, current route, and/or currentdestination, and/or type of emergency, such as a vehicle accident orweather event; and/or (2) broadcasting or transmitting, via or at one ormore processors or an associated transceiver mounted on the emergencyresponse vehicle, the emergency response vehicle data, such as viawireless communication or data transmission, to non-emergency responsevehicles or remote servers to facilitate one or more of thenon-emergency response vehicles generating warnings associated with theemergency response vehicle and/or alternate routes to avoid the path ofthe emergency response vehicle to facilitate alleviating potentialvehicle accidents between emergency response and non-emergency responsevehicles, and/or shortening emergency response times for emergencyresponse vehicles.

The method may further include adjusting an insurance policy, premium,rate, or discount for the emergency response vehicle based upon thenon-emergency response vehicle having the emergency response vehicledata generation and/or broadcast functionality. The method may includeadditional, less, or alternate functionality, including that discussedelsewhere herein, and/or the method may be implemented via a computersystem, communication network, one or more processors, and/orcomputer-executable instructions stored on non-transitory storage mediaor computer-readable medium.

Exemplary Warning and Alternate Route Generation

In one aspect, a computer implemented method for generating datarepresentative of an emergency vehicle warning and/or alternate vehicleroute may be provided. The method may include: (1) receiving, via or atone or more processors associated with, or mounted on, a non-emergencyvehicle, emergency vehicle data via wireless communication or datatransmission, wherein the emergency vehicle data is representative of:emergency vehicle (i) origination, (ii) current location, (iii) currentspeed, (iv) current heading, (v) current route, and/or (vi) currentdestination, and/or (vii) type of emergency, such as a vehicle accident,house fire, medical emergency, or weather event; (2) generating orcollecting, via or at the one or more processors associated with, ormounted on, the non-emergency vehicle, non-emergency vehicle data fromone or more vehicle-mounted sensors, wherein the non-emergency vehicledata is representative of: non-emergency vehicle (a) origination, (b)current location, (c) current speed, (d) current heading, (e) currentroute, and/or (f) current destination; (3) generating, via or at the oneor more processors associated with, or mounted on, the non-emergencyvehicle, emergency vehicle warning data and/or alternate vehicle routedata based upon computer analysis or comparison of the emergency andnon-emergency vehicle data that is performed by the one or moreprocessors associated with the non-emergency vehicle, the alternatevehicle route directing the non-emergency vehicle to avoid the route ofthe emergency vehicle, or otherwise alleviates an amount that thenon-emergency vehicle interferes with a route of the emergency vehicle;and/or (4) causing, via or at the one or more processors associatedwith, or mounted on, the non-emergency vehicle, the emergency vehiclewarning data and alternate vehicle route data, to be visually or audiblypresented, or otherwise provided, to a driver of the non-emergencyvehicle to facilitate alleviating potential vehicle accidents betweenemergency response and non-emergency response vehicles, and/orshortening emergency response times for emergency vehicles.

The method may also include adjusting an insurance policy, premium,rate, or discount for the non-emergency vehicle based upon thenon-emergency vehicle having the vehicle warning and/or alternatevehicle route generation functionality. The non-emergency vehicle may bean autonomous or smart vehicle, and the autonomous or smart vehicle mayautomatically direct itself to take an alternate vehicle route and takeself-driving actions that allow the autonomous or smart vehicle avoidthe emergency vehicle or the route of the emergency vehicle.

The method may include adjusting an insurance policy, premium, rate, ordiscount for the autonomous, non-emergency response vehicle based uponthe autonomous, non-emergency response vehicle having the vehiclewarning and/or alternate vehicle route generation functionality.Additionally or alternatively, the method may include adjusting aninsurance policy, premium, rate, or discount for the emergency responsevehicle based upon the emergency response vehicle having the emergencyresponse vehicle data generation and/or broadcast functionality.

The method may include generating, via the one or more processorsmounted on the non-emergency vehicle, insurance policy data for thedriver of the non-emergency vehicle based upon the driver followingrecommendations associated with emergency vehicle warnings or alternatevehicle routing that avoids emergency vehicles en route, and/ortransmitting, via the one or more processors mounted on thenon-emergency vehicle, to an insurance provider remote server tofacilitate the insurance provider (or insurance provider remote server)providing auto insurance cost savings to the driver (or other insured orvehicle owner) based upon the insurance policy data and/or functionalityassociated with emergency vehicle avoidance. The method may includeadditional, less, or alternate functionality, including that discussedelsewhere herein, and/or the method may be implemented via a computersystem, communication network, one or more processors, and/orcomputer-executable instructions stored on non-transitory storage mediaor computer-readable medium.

Exemplary Vehicle Mounted System

In another aspect, a vehicle-mounted system of a non-emergency vehiclefor generating emergency vehicle warning data and/or alternate routedata may be provided. The system may include one or more processorsmounted on the non-emergency vehicle configured to: (1) receiveemergency vehicle data via wireless communication or data transmission,the emergency vehicle data being representative of: emergency vehicle(i) origination location, (ii) current location data, (iii) route, (iv)destination, (v) speed, and/or (vi) alternate routing; (2) generate orcollect non-emergency vehicle data, the non-emergency vehicle dataassociated with the non-emergency vehicle and being generated by one ormore vehicle-mounted sensors or processors, the non-emergency vehicledata is representative of: non-emergency vehicle (a) originationlocation, (b) current location, (c) route, (d) destination, and/or (e)speed; (3) generate an alternate route based upon computer analysis orcomparison of the emergency vehicle data and the non-emergency vehicledata; and/or (4) present the alternate route to the driver of thevehicle, or the vehicle itself, such that the driver of the vehicle, orthe vehicle itself, may avoid the route of the emergency vehicle or thatshortening of the response time for emergency vehicles is facilitated.

The non-emergency vehicle may be an autonomous vehicle thatautomatically avoids the route of the emergency vehicle based uponcomputer comparison or analysis of the emergency and non-emergencyvehicle data. Additionally or alternatively, the emergency vehicle maybe an autonomous vehicle that automatically avoids the route of thenon-emergency vehicle based upon computer comparison or analysis of theemergency and non-emergency vehicle data.

The one or more processors mounted on the non-emergency vehicle may befurther configured to: collect or generate, via the one or moreprocessors mounted on the non-emergency vehicle, insurance policy datafor the driver of the non-emergency vehicle based upon the driverfollowing recommendations associated with emergency vehicle warnings oralternate vehicle routing that avoids emergency vehicles en route,and/or transmit, via the one or more processors mounted on thenon-emergency vehicle, the insurance policy data to an insuranceprovider remote server to facilitate the insurance provider or insuranceprovider remote server providing auto insurance cost savings to thedriver (or other insured or vehicle owner) based upon the insurancepolicy data and/or functionality associated with emergency vehicleavoidance.

The one or more processors mounted on the non-emergency vehicle may befurther configured to: generate an emergency vehicle warning based uponcomputer analysis or comparison of the emergency vehicle data and thenon-emergency vehicle data; and/or present the emergency vehicle warningto the driver of the vehicle such that the driver of the vehicle, or thevehicle itself, may avoid the route of the emergency vehicle or thatshortening of the response time for emergency vehicles is facilitated.The vehicle-mounted system may include additional, less, or alternateactions, including those discussed elsewhere herein.

Additional Considerations

Although the following text sets forth a detailed description ofnumerous different embodiments, it should be understood that the legalscope of the description is defined by the words of the claims set forthat the end of this patent and equivalents. The detailed description isto be construed as exemplary only and does not describe every possibleembodiment since describing every possible embodiment would beimpractical. Numerous alternative embodiments may be implemented, usingeither current technology or technology developed after the filing dateof this patent, which would still fall within the scope of the claims.

The following additional considerations apply to the foregoingdiscussion. Throughout this specification, plural instances mayimplement components, operations, or structures described as a singleinstance. Although individual operations of one or more methods areillustrated and described as separate operations, one or more of theindividual operations may be performed concurrently, and nothingrequires that the operations be performed in the order illustrated.Structures and functionality presented as separate components in exampleconfigurations may be implemented as a combined structure or component.Similarly, structures and functionality presented as a single componentmay be implemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Additionally, certain embodiments are described herein as includinglogic or a number of routines, subroutines, applications, orinstructions. These may constitute either software (e.g., code embodiedon a machine-readable medium or in a transmission signal) or hardware.In hardware, the routines, etc., are tangible units capable ofperforming certain operations and may be configured or arranged in acertain manner. In example embodiments, one or more computer systems(e.g., a standalone, client or server computer system) or one or morehardware modules of a computer system (e.g., a processor or a group ofprocessors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules may provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connect the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and may operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods or routines described herein may be at leastpartially processor-implemented. For example, at least some of theoperations of a method may be performed by one or more processors orprocessor-implemented hardware modules. The performance of certain ofthe operations may be distributed among the one or more processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or a combination thereof), registers, or othermachine components that receive, store, transmit, or displayinformation.

As used herein any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. For example, some embodimentsmay be described using the term “coupled” to indicate that two or moreelements are in direct physical or electrical contact. The term“coupled,” however, may also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other. The embodiments are not limited in this context.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

In addition, use of the “a” or “an” are employed to describe elementsand components of the embodiments herein. This is done merely forconvenience and to give a general sense of the description. Thisdescription, and the claims that follow, should be read to include oneor at least one and the singular also includes the plural unless it isobvious that it is meant otherwise.

This detailed description is to be construed as exemplary only and doesnot describe every possible embodiment, as describing every possibleembodiment would be impractical, if not impossible. One may be implementnumerous alternate embodiments, using either current technology ortechnology developed after the filing date of this application.

What is claimed is:
 1. A computer implemented method for generating data representative of an emergency vehicle warning and/or alternate vehicle route, the method comprising: receiving, via or at one or more processors mounted on a non-emergency vehicle, emergency vehicle data via wireless communication and/or data transmission, wherein the emergency vehicle data is representative of an emergency vehicle route; determining emergency vehicle warning data and an alternate vehicle route data, via or at the one or more processors mounted on the non-emergency vehicle, wherein the alternate vehicle route directs the non-emergency vehicle to avoid the route of the emergency vehicle or otherwise alleviates an amount that the non-emergency vehicle interferes with the route of the emergency vehicle; causing, via or at the one or more processors mounted on the non-emergency vehicle, the emergency vehicle warning data and alternate vehicle route data, to be visibly or audibly presented, or otherwise provided, to a driver of the non-emergency vehicle to facilitate alleviating potential vehicle accidents between emergency response and non-emergency response vehicles, and/or shortening emergency response times for emergency vehicles; receiving, via the one or more processors mounted on the non-emergency vehicle, an opt-in selection, wherein the opt-in selection is representative of a content of desired insurance policy related data and exclusion of personal information; generating, via the one or more processors mounted on the non-emergency vehicle, insurance policy data for the driver of the non-emergency vehicle based upon the opt-in selection and further based upon the driver following recommendations associated with emergency vehicle warnings or alternate vehicle routing that avoids emergency vehicles en route; and transmitting, via the one or more processors mounted on the non-emergency vehicle, to an insurance provider remote server to facilitate the insurance provider providing auto insurance cost savings to the driver or other insured based upon the insurance policy data and/or functionality associated with emergency vehicle avoidance.
 2. The computer implemented method of claim 1, wherein the vehicle warning data is representative of at least one of: an audible warning to stop, a visual warning to stop, an audible warning to move right, a visual warning to move right, an audible warning to move left, a visual warning to move left, an audible warning to move onto a shoulder of a road, a visual warning to move onto a shoulder of a road, an audible warning to merge to a right lane, a visual warning to merge to a right lane, or an audible warning to duplicate a siren tone.
 3. The computer implemented method of claim 1, wherein the insurance policy data is representative of an insurance risk associated with a non-emergency vehicle, and the insurance risk is lower for a non-emergency vehicle that is equipped with an emergency vehicle warning data receiving device.
 4. The computer implemented method of claim 1, wherein the insurance policy data is representative of an insurance risk associated with an emergency vehicle, and the insurance risk is lower for an emergency vehicle that is equipped with an emergency vehicle warning data generation, transmitting, and/or receiving device.
 5. The computer implemented method of claim 1, further comprising: transmitting, via the one or more processors mounted on the non-emergency vehicle, emergency vehicle warning data and alternate vehicle route data to other vehicles or processors.
 6. The computer implemented method of claim 1, wherein the non-emergency vehicle is an autonomous or smart vehicle, and the autonomous or smart vehicle automatically directs itself to take an alternate vehicle route and take self-driving actions that allow the autonomous or smart vehicle avoid the emergency vehicle or the route of the emergency vehicle.
 7. The computer implemented method of claim 1, wherein the emergency vehicle is an autonomous or smart vehicle, and the autonomous or smart vehicle automatically directs itself to take an alternate vehicle route and take self-driving actions that allow the autonomous or smart vehicle avoid the non-emergency vehicle or the route of the non-emergency vehicle.
 8. The computer implemented method of claim 1, the method further comprising adjusting an insurance policy, premium, rate, or discount for the non-emergency vehicle based upon the non-emergency vehicle having the vehicle warning and/or alternate vehicle route generation functionality.
 9. A vehicle-mounted system of a non-emergency vehicle for generating emergency vehicle warning data and/or alternate route data, the system comprising one or more processors mounted on the non-emergency vehicle configured to: receive emergency vehicle data via wireless communication or data transmission, wherein the emergency vehicle data is representative of an emergency vehicle route; generate an alternate route based upon computer analysis or comparison of the emergency vehicle data and non-emergency vehicle data, the non-emergency vehicle data associated with a route and current location of the non-emergency vehicle; present the alternate route to the driver of the vehicle, or the vehicle itself, such that the driver of the vehicle, or the vehicle itself, may avoid the route of the emergency vehicle or that shortening of the response time for emergency vehicles is facilitated; receive, via the one or more processors mounted on the non-emergency vehicle, an opt-in selection, wherein the opt-in selection is representative of a content of desired insurance policy related data and exclusion of personal information; at least one of: collect insurance policy data for the driver of the non-emergency vehicle or generate insurance policy data for the driver of the non-emergency vehicle, via the one or more processors mounted on the non-emergency vehicle, wherein the insurance policy data for the driver of the non-emergency vehicle is based upon the opt-in selection and further based upon the driver following recommendations associated with emergency vehicle warnings or alternate vehicle routing that avoids emergency vehicles en route, and transmit, via the one or more processors mounted on the non-emergency vehicle, the insurance policy data to an insurance provider remote server to facilitate the insurance provider providing auto insurance cost savings to the driver or other insured based upon the insurance policy data and/or functionality associated with emergency vehicle avoidance.
 10. The system of claim 9, wherein the non-emergency vehicle is an autonomous vehicle that automatically avoids the route of the emergency vehicle based upon computer comparison or analysis of the emergency and non-emergency vehicle data.
 11. The system of claim 9, wherein the emergency vehicle is an autonomous vehicle that automatically avoids the route of the non-emergency vehicle based upon computer comparison or analysis of the emergency and non-emergency vehicle data.
 12. The system of claim 9, the one or more processors mounted on the non-emergency vehicle further configured to: generate vehicle warning data based upon the computer analysis or the comparison of the emergency vehicle data and the non-emergency vehicle data, wherein the vehicle warning data is representative of at least one of: an audible warning to stop, a visual warning to stop, an audible warning to move right, a visual warning to move right, an audible warning to move left, a visual warning to move left, an audible warning to move onto a shoulder of a road, a visual warning to move onto a shoulder of a road, an audible warning to merge to a right lane, a visual warning to merge to a right lane, or an audible warning to duplicate a siren tone.
 13. The system of claim 9, the one or more processors mounted on the non-emergency vehicle further configured to: generate an emergency vehicle warning based upon computer analysis or comparison of the emergency vehicle data and the non-emergency vehicle data; and/or present the emergency vehicle warning to the driver of the vehicle such that the driver of the vehicle, or the vehicle itself, may avoid the route of the emergency vehicle or that shortening of the response time for emergency vehicles is facilitated.
 14. A computer implemented method for generating data representative of an emergency vehicle warning and/or alternate vehicle route, the method comprising: receiving, via or at one or more processors associated with, or mounted on, a non-emergency vehicle, emergency vehicle data via wireless communication or data transmission, wherein the emergency vehicle data is representative of an emergency vehicle route; generating, via or at the one or more processors associated with, or mounted on, the non-emergency vehicle, emergency vehicle warning data and alternate vehicle route data based upon computer analysis or comparison of the emergency vehicle data with non-emergency vehicle data, the non-emergency vehicle data including a route and current location of the non-emergency vehicle; causing, via or at the one or more processors associated with, or mounted on, the non-emergency vehicle, the emergency vehicle warning data and alternate vehicle route data, to be visually or audibly presented, or otherwise provided, to a driver of the non-emergency vehicle to facilitate alleviating potential vehicle accidents between emergency response and non-emergency response vehicles; receiving, via or at the one or more processors associated with, mounted on, the non-emergency vehicle, an opt-in selection, wherein the opt-in selection is representative of a content of desired insurance policy related data and exclusion of personal information; generating, via or at the one or more processors associated with, or mounted on, the non-emergency vehicle, insurance policy data for the driver of the non-emergency vehicle based upon the opt-in selection and further based upon the driver following recommendations associated with emergency vehicle warnings or alternate vehicle routing that avoids emergency vehicles en route; and transmitting, via or at the one or more processors associated with, or mounted on, the non-emergency vehicle, to an insurance provider remote server to facilitate the insurance provider providing auto insurance cost savings to the driver or other insured based upon the insurance policy data and/or functionality associated with emergency vehicle avoidance.
 15. The computer implemented method of claim 14, the method further comprising adjusting an insurance policy, premium, rate, or discount for the non-emergency vehicle based upon the non-emergency vehicle having the vehicle warning and/or alternate vehicle route generation functionality.
 16. The computer implemented method of claim 14, wherein the non-emergency vehicle is an autonomous or smart vehicle, and the autonomous or smart vehicle automatically directs itself to take an alternate vehicle route and take self-driving actions that allow the autonomous or smart vehicle avoid the emergency vehicle or the route of the emergency vehicle.
 17. The computer implemented method of claim 14, the method further comprising adjusting an insurance policy, premium, rate, or discount for an autonomous, non-emergency response vehicle based upon the autonomous, non-emergency response vehicle having the vehicle warning and/or alternate vehicle route generation functionality.
 18. The computer implemented method of claim 14, the method further comprising adjusting an insurance policy, premium, rate, or discount for the emergency response vehicle based upon the emergency response vehicle having the emergency response vehicle data generation and/or broadcast functionality.
 19. The computer implemented method of claim 14, further comprising: generating, via the one or more processors mounted on the non-emergency vehicle, insurance policy data for the driver of the non-emergency vehicle based upon the driver following recommendations associated with emergency vehicle warnings or alternate vehicle routing that avoids emergency vehicles en route.
 20. The computer implemented method of claim 19, further comprising: transmitting, via the one or more processors mounted on the non-emergency vehicle, to an insurance provider remote server to facilitate the insurance provider providing auto insurance cost savings to the driver or other insured based upon the insurance policy data and/or functionality associated with emergency vehicle avoidance. 